perm filename THROW.DOC[HAL,HE] blob sn#065289 filedate 1973-09-29 generic text, type T, neo UTF8
00100	MY WAVE HAS A BLOCK FOR FUNNAMS 50 AND 51, I THINK, FOR THROW
00200	AND TOSS, RESPECTIVELY.  
00300	THROW expects these arguments: Release point [1:4,1:4],
00400		Velocity [1:4], Final point [1:4,1:4],
00500		two reals, which I suggest you set to 0 (they are the
00600		accelearations just before and just after the release
00700		segment),
00800		and a boolean SUCCESS.
00900	THROW works, with these provisoes:  The limits of velocity are
01000		set a bit stringently, so some perfectly good motions are 
01100		not even attempted.  There is no checking whatsoever for
01200		intersections with the table, although this can be put in,
01300		as procedures INSPECT_FIRST and INSPECT_SECOND.  On some/
01400		lofting throws, the arm goes through the table.
01500	What THROW is intended to do is to get the arm at the given release
01600		point and at the intended x-y-z velocity, the motion to ter-
01700		minate at the final point.
01800	
01900	TOSS expects release point, target [1:4], in which the x-y-z coor-
02000		dinates of the target reside, the final point of the motion,
02100		the muzzle velocity (inches / jiffy), and the same two accel-
02200		eration reals as in THROW.
02300	TOSS works.  It has an accuracy of about 2 inches at farthest throw,
02400		and about one inch at closer ones.
02500	WAVE.DMP[1,RF] is the latest version to use.